Skip to content

use completionProvider and seperate value and key completion. - #67

Draft
srivastava-diya wants to merge 4 commits into
hyperjump-io:mainfrom
srivastava-diya:value-completion-simple
Draft

use completionProvider and seperate value and key completion.#67
srivastava-diya wants to merge 4 commits into
hyperjump-io:mainfrom
srivastava-diya:value-completion-simple

Conversation

@srivastava-diya

Copy link
Copy Markdown
Collaborator

Description

  • Split into providers, Completion.ts became a orchestrator so PropertyCompletion.ts and ValueCompletion.ts became separate files.

  • Capturing type as an annotation, removing schemaStore lookup entirely

  • seperated Completion.test.ts file into ValueCompletion.test.ts and PropertyCompletion.test.ts

Comment thread language-server/src/features/PropertyCompletion.test.ts Outdated
continue;
}

if (type === "number" || type === "integer") {

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

skipping this for integer and number because there's nothing to show in the suggestion

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just skipping sounds like it might be misleading. The user might be using those suggestions to know what to write next and if number/integer doesn't show up, they might think it's not allowed or not expected.

I wonder if it would be better to include those options, but just return a space.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i have removed the special if case for integer and number from the loop, now we just show options with label "number"/"integer" which returns a space

Screen.Recording.2026-08-08.032717.mp4

Comment thread language-server/src/features/ValueCompletion.ts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants